This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@cloudflare/[email protected]

Minor Changes

• #8514 4ad78ea Thanks @vicb! - Use the native implementation for connect and TLSSocket from node:tls

[email protected]

Minor Changes

• #8477 fd9dff8 Thanks @gabivlj! - wrangler deploy includes container configuration when uploading the script

Patch Changes

• #8220 14680b9 Thanks @IRCody! - Fix a bug in cloudchamber build where it would still attempt to push an image if the build failed.

• #8186 05973bb Thanks @IRCody! - Add cloudchamber images {list,delete} commands to list and delete images stored in cloudchamber managed registry.

• Updated dependencies [ff26dc2, 4ad78ea]:

  • [email protected]
  • @cloudflare/[email protected]

[email protected]

Patch Changes

• #8379 2b37abe Thanks @emily-shen! - Graduate Workers + Assets hello world templates from experimental status

• #8541 cfa525d Thanks @GregBrimble! - fix: Fixes the Cloudflare logo in the Vite React starter to support both dark and light mode

[email protected]

Patch Changes

• #8357 ff26dc2 Thanks @dario-piotrowicz! - feat: add new unsafeInspectorProxy option to miniflare

  Add a new unsafeInspectorProxy option to the miniflare worker options, if
  at least one worker has the option set then miniflare will establish a proxy
  between itself and workerd for the v8 inspector APIs which exposes only the
  requested workers to inspector clients. The inspector proxy communicates through
  miniflare's inspectorPort and exposes each requested worker via a path comprised
  of the worker's name

  example:

  import { Miniflare } from "miniflare";
  
  const mf = new Miniflare({
  	// the inspector proxy will be accessible through port 9229
  	inspectorPort: 9229,
  	workers: [
  		{
  			name: "worker-a",
  			scriptPath: "./worker-a.js",
  			// enable the inspector proxy for worker-a
  			unsafeInspectorProxy: true,
  		},
  		{
  			name: "worker-b",
  			scriptPath: "./worker-b.js",
  			// worker-b is not going to be proxied
  		},
  		{
  			name: "worker-c",
  			scriptPath: "./worker-c.js",
  			// enable the inspector proxy for worker-c
  			unsafeInspectorProxy: true,
  		},
  	],
  });

  In the above example an inspector proxy gets set up which exposes worker-a and worker-b,
  inspector clients can discover such workers via http://localhost:9229 and communicate with
  them respectively via ws://localhost:9229/worker-a and ws://localhost:9229/worker-b

  Note: this API is experimental, thus it's not being added to the public documentation and
  it's prefixed by unsafe

@cloudflare/[email protected]

Patch Changes

• Updated dependencies [ff26dc2]:
  • [email protected]

@cloudflare/[email protected]

Patch Changes

• #8505 03435cc Thanks @jamesopstad! - Support Wrangler v4 as peer dependency.

• #8523 c7f86cb Thanks @dario-piotrowicz! - add validation for the Wrangler config main field

• #8515 3d69e52 Thanks @jamesopstad! - Set target in optimizeDeps.esbuildOptions to es2022. This fixes a bug where the target for prebundled dependencies did not match the build target.

• Updated dependencies [14680b9, fd9dff8, ff26dc2, 05973bb, 4ad78ea]:

  • [email protected]
  • [email protected]
  • @cloudflare/[email protected]

@cloudflare/[email protected]

Patch Changes

• Updated dependencies [14680b9, fd9dff8, ff26dc2, 05973bb]:
  • [email protected]
  • [email protected]